------------------------------------------------------------
              PureEdge(TM) Viewer version 6.5.0
                   
	                      Release Notes
		                             
                   Updated:  June 20 2005
------------------------------------------------------------

Copyright 2005 PureEdge Solutions Incorporated. All rights
reserved.

Please read the licenses.txt file before using this 
software.

This document provides last-minute product information for 
PureEdge Viewer version 6.5.0.

------------------------------------------------------------


--------
Contents
--------

1.  New Features and Changes

	1.1  Version 6.5.0
	1.2  Version 6.4.0
	1.3  Version 6.3.0
	1.4  Version 6.2.0
	1.5  Version 6.1.0
	1.6  Version 6.0.2
	1.7  Version 6.0.1
	1.8  Version 6.0.0
	     1.8.1  XFDL Changes
	     1.8.2  Viewer Features
	1.9  Version 5.2.0 (Limited Release)
	1.10 Version 5.1.1
	1.11 Version 5.1.0

2.  Known Issues

	2.1  Users
	2.2  Developers

3.  Other Usage Notes

4.  Troubleshooting

	4.1  Installation
	4.2  Printing
	4.3  Web Browsers
	4.4  Emailing Forms


============================
1.  NEW FEATURES AND CHANGES
============================

------------------
1.1  Version 6.5.0
------------------

1.1.1  Support for XFDL 6.5

  The Viewer now supports XFDL version 6.5.  Note that the 
  namespace URL for XFDL version 6.5 is:

  http://www.PureEdge.com/XFDL/6.5

1.1.2  Support for Silanis Signatures

  The Viewer now supports Silanis signatures.  This includes
  a No-Lock feature that is specific to Silanis signatures.
  
  When a Silanis signature is set to No-Lock, the data that 
  is signed is not locked in the Viewer.  In other words, 
  the user can change that data in the Viewer even though 
  it has already been signed.  This will invalidate the 
  signature, but the changes can then be approved by a 
  second signature.  For more information about these 
  signatures, refer to the PureEdge Viewer User's Manual.
  
  No-Lock signatures are created by adding a "lock" 
  parameter to the signformat option for Silanis signatures.  
  For more information, refer to the XFDL Specification.
  
  Before you can sign a form using a Silanis signature, you 
  must install the ApproveIt Desktop software from Silanis.

1.1.3  Support for No-Delete Signatures

  The Viewer now supports No-Delete signatures.  Any 
  signature type can be set to No-Delete, which means that 
  the signature cannot be deleted through the signature 
  dialog.  For more information about No-Delete signatures, 
  refer to the PureEdge Viewer User's Manual.

  No-Delete signatures are created by adding a "delete" 
  parameter to the signformat option.  For more information,
  refer to the XFDL Specification.

1.1.4  New Toolbar Functionality

  The Viewer now has two save buttons in the toolbar: "Save 
  Form" and "Save As". The Save Form button now saves the 
  form to the current file without prompting the user.  The 
  Save As button prompts the user for a filename and 
  location before saving the form.
  
  Additionally, the following hotkey now triggers a Save 
  As:  SHIFT + CTRL + S.
  
  If you are using the ufv_settings option to control the 
  appearance of the save button, be aware that both save 
  buttons are now controlled by the "save" flag in the menu 
  setting.  See the "Using Viewer Settings" document for 
  more information.

1.1.5  Printing Headers and Footers

  The Viewer now supports printing multi-line headers and 
  footers.  Additionally, the Viewer now scales headers and 
  footers more accurately when shrinking them to fit the 
  page (see section 3.8).  For more information about using 
  headers and footers, refer to the Using Viewer Functions 
  document.

1.1.6  Changed Settings for type Option

  The Viewer now respects settings of "saveform" and 
  "saveas" for the type option.  "saveform" saves the 
  form to the current file, while "saveas" prompts the
  user for a filename and location before saving.
  
  Note that if a form has been opened from the web, 
  "saveform" will prompt the user for a filename and 
  location, because these are not set until the form
  has been saved for the first time.
    
  The "save" setting, which behaves like saveas, has been 
  deprecated.  As such, future versions of the Viewer may 
  drop support for it, and you should update your forms to 
  use the new settings. 

1.1.7  File Extension

  The Viewer now defaults to using the .xfdl file extension
  rather than .xfd.  This addresses some incompatabilities 
  with other software that also uses the .xfd extension.
  
  When a form is opened, the Viewer will maintain the 
  original extension for the form.  However, when the 
  Viewer writes temporary files, or if the Viewer saves a
  file that does not already have an extension set, it 
  will default to .xfdl.

  The Viewer still supports the .xfd extension, and will 
  continue to do so in the future.

1.1.8  Fixed Issue When Verifying Certificate Chains

  When the Viewer checks a certificate chain, it normally 
  creates the chain by matching the Authority Key Identifier
  of the certificate to the Subject Key Identifier of the 
  Issuer.  However, in cases in which the issuing 
  certificate does not have a Subject Key Identifier but 
  the issued certificate has an Authority Key Identifier 
  (such as when a version1 certificate is used to create a 
  version3 certificate), this check was failing.
  
  In these cases, the Viewer will now fall back on matching
  certificate names to create the chain.  This method is 
  already used when neither the certificate nor the issuer
  has the proper extensions.

------------------
1.2  Version 6.4.0
------------------

1.2.1  Support for XFDL 6.4

  The Viewer now supports XFDL version 6.4.  Note that the 
  namespace URL for XFDL version 6.4 is:

  http://www.PureEdge.com/XFDL/6.4

1.2.2  Support for Signature Pad Signatures

  The Viewer now allows users to sign forms by using 
  hardware that captures their written signature, called 
  a signature pad.
  
  Users require signature pad hardware and software (such as 
  that available from Interlink or Topaz), as well as a 
  special add-on to the Viewer, before they can use 
  signature pads.  However, the Viewer will verify 
  signature pad signatures with no additional hardware
  or software.
  
  For more information about this type of signature, refer 
  to the following documents:
  
  - XFDL Specification (signformat option)
  - Creating Digital Signature Buttons in XFDL
  - Best Practices for Form Design
  
  For more information about the Viewer add-on, contact 
  PureEdge Support.

1.2.3  Dropped Support for CIC Signatures
 
  The Viewer no longer supports CIC signatures.

1.2.4  Fixed Problem with Toggle

  Fixed a problem with the toggle function that occurred 
  only when using pre-6.0 forms with a version 6.0 or later 
  API.  In this case, instance data associated with the 
  toggle was not properly deregistered.  This could cause 
  odd behavior with the toggle function if a single instance
  of a program, such as a servlet using the PureEdge API, 
  loaded a form multiple times and evaluated the computes
  in that form.  This could also affect the performance of 
  any custom Viewer extensions (.ifx files) that maintained 
  instance data.

  Note that this problem did not directly affect the Viewer,
  as a different instance of the Viewer is launched for each
  form viewed.  However, as mentioned, custom Viewer 
  extensions may have been affected.

------------------
1.3  Version 6.3.0
------------------

1.3.1  Updated to Work in Restricted User Mode

  The Viewer now relies on different registry settings, 
  which enables it to work in more restrictive modes than
  regular User mode.

1.3.2  Installer Removes Previous Viewers

  The Viewer's installer now attempts to remove all previous 
  versions of the Viewer from the computer.  This ensures 
  that the right registry entries are being used.
  
  Running an older version of the Viewer will reset the 
  registry entries, and will prevent the new Viewer from 
  running properly.

1.3.3  Preferences Migration

  This version of the Viewer will copy the preferences
  from the most recent version of the Viewer already 
  installed on the computer.

1.3.4  Fixed Memory Leak

  Fixed a memory leak that occurred when a digital signature
  could not be verified.

1.3.5  Fixed Decompression Problem

  Fixed a problem that prevented base64-gzip compressed 
  forms and enclosures from decompressing properly if they
  were larger than 25 million bytes in size.

1.3.6  Removed Support for signarrayrefs Option

  The Viewer no longer supports the signarrayrefs option.
  Furthermore, the Viewer does not offer backward 
  compatibility for this option, regardless of the 
  version of XFDL in use.

------------------
1.4  Version 6.2.0
------------------

1.4.1  Support for XFDL 6.2

  The API now supports XFDL version 6.2.  Note that the 
  namespace URL for XFDL version 6.2 is:

  http://www.PureEdge.com/XFDL/6.2

1.4.2  Support for Portal Environments

  The Viewer can now be embedded in an HTML page through
  use of the HTML <object> tag, allowing the Viewer to return
  XFDL data from a portal environment.
   
  Note that this feature is only supported in Internet Explorer 
  6.0 browsers. 
   
  For more information refer to the guide entitled, "Embedding 
  the Viewer in HTML".
   
1.4.3  Support for Netscape 7.1 Certificates   

  The Viewer now supports the new Netscape 7.1 certificate 
  database. Older Netscape certificate databases and older 
  versions of Netscape certificates imported into the new database 
  are also supported.
   
1.4.4  Support for Mozilla Browsers

  The Viewer now supports Mozilla 1.7.
  
1.4.5  Improved Smartfill Support

  The Viewer now supports the active option for data fragments.
  This allows form designers to specify which data fragments are 
  loaded when the form is opened. This is particularly useful when
  creating forms intended for use by multiple users. For example, 
  in a workflow, Smartfill can automatically add user information 
  to the form as it is opened by each successive user.
  
  You can disable the Smartfill feature in the Input 
  preferences for the Viewer.
  
  For more information, refer to the PureEdge Viewer 
  User's Manual and the guide entitled, "Using the XML Data
  Model."
  
1.4.6  Support for signarrayrefs Option

  The Viewer now supports the signarrayrefs option. This 
  option specifies individual arrays that are filtered for 
  a particular signature. 
  
  For more information, refer to the XFDL Specification.  
  
1.4.7  Support for empty Function in getGroupedItem

  The Viewer now supports the empty function as the third 
  parameter of the getGroupedItem function. This allows 
  getGroupedItem to return items that contain empty values 
  in the specified option.  
  
  For example:
  
   getGroupedItem('Page1.radioGroup', 'value', empty())
  
  For more information, refer to the XFDL Specification.
  
1.4.8  Improved Tablet Support

  Fixed a problem with stylus entry into fields with templates.
  Previously, templated fields could not recognize stylus 
  entries.
    
  Some limitations continue to exist:
  
  - Cannot paste a string into a field with a template.
  - Cannot highlight and replace characters with a stylus.
  - Cannot undo in a field with a template.
  
1.4.9  Support for New Viewer Functions

  The Viewer now supports the following Viewer functions:
  
  - param - Returns the parameter value of the HTML object 
            tag when the Viewer is embedded in an HTML page.

  - env - Returns a string that contains the details of 
          the current operating environment.
                
  For more information, refer to the guide entitled, "Using
  Viewer Functions".  
  
1.4.10  Fixed Problems with Actions

  Fixed two problems regarding actions:
  - Corrected problem where actions with a delay of '-1' 
    prevented subsequent actions from activating. 
  - Corrected problem where actions with a delay of  
    'once' were not activating.
 
1.4.11  Fixed Problem with Double Submits

  Fixed a problem when using submit buttons with Netscape 7.x
  browsers. Using a button which performed a Post submission
  caused the submit to occur twice.
  
1.4.12  Fixed Problem with activated Option

  Fixed a problem that was introduced in version 6.1. This 
  problem prevented the activated option from operating 
  correctly, so that buttons, cells, and actions did not always 
  trigger correctly. 
  
1.4.13  Fixed Problem with signnamespaces Option

  Fixed a problem in Viewers 6.0 and 6.1 where the signnamespaces
  option was not correctly implemented. This problem prevented
  namespaces from being filtered by the signature. 
  
  Refer to the XFDL specification for more information. 
  
1.4.14  Fixed Problem with Verifying Signatures Signed in pre-6.0 
	Viewers 
  
  Fixed a problem that was introduced in Viewers 6.0. This issue
  sometimes prevented the Viewer from verifying signatures in forms 
  older than 4.4 that were signed in pre 6.0 Viewers.
  
------------------
1.5  Version 6.1.0
------------------

1.5.1  Support for XFDL 6.1

  The Viewer now supports XFDL version 6.1.  Note that the 
  namespace URL for XFDL version 6.1 is:

  http://www.PureEdge.com/XFDL/6.1

1.5.2  Schema Support

  The Viewer now supports the use of schemas for validating
  the XML Data Model in an XFDL form.  For more information,
  refer to the guide entitled, "Using the XML Data Model".
  
1.5.3  Support for webservices Option and Web Services

  The Viewer now supports the inclusion of Web Services 
  in XFDL forms.  This allows you to use Web Services 
  within a form as though they were regular XFDL functions.
  For more information, refer to webservices option in the 
  XFDL Specification.

1.5.4  New Smartfill Feature

  The Viewer now offers a new feature called Smartfill.  
  This feature uses locally stored data to automatically 
  complete portions of a form for you.  For example, 
  SmartFill can automatically add your name and address to 
  a form that you are filling out.  
  
  You can disable the Smartfill feature in the Input 
  preferences for the Viewer.
  
  For more information, refer to the PureEdge Viewer 
  User's Manual and the guide entitled, "Using the XML Data
  Model."
  
1.5.5  New Requirements Feature

  The Viewer now checks each form for individual 
  requirements while opening the form for the user.  This
  means that forms may list specific functionality - such 
  as a Java Virtual Machine or a particular form extension 
  (.ifx file) - that must be present before the Viewer can 
  run them properly.  For more information, refer to the 
  PureEdge Viewer User's Manual and the XFDL Specification.
  
1.5.6  Support for New Calendar Widget

  The Viewer now supports a calendar widget.  This allows
  the user to pick a date from a calendar rather than typing
  in a date.
  
  You can create a calendar widget in two ways:
  
  - Create a combobox with no cells, and give it a date 
    format.
    
  - Use the showCalendar function.
  
  For more information, refer to the XFDL Specification.

1.5.7  Support for New XFDL Functions

  The Viewer now supports the following XFDL functions:

  - countChildren - counts the number of children that 
       belong to a particular element, such as a page or
       an item in the form.

  - for - creates a loop similar to the "for loop" found
       in most programming languages.

  - getInstanceRef - returns the reference for a particular
       instance in the XML Data Model.

  - xmlModelValidate - validates the XML model against one 
       or more supplied schema.

  For more information about these functions, refer to the 
  XFDL Specification.

1.5.8  Support for New Viewer Functions

  The Viewer now supports the following XFDL functions:
  
  - getY - Determines the pixel location for the top of 
        the item.
        
  - getX - Determines the pixel location for the left edge
        of the item.

  - getWidth - Determines the width of an item.
  
  For more information about these functions, refer to the 
  guide entitled, "Using Viewer Functions".
  
1.5.9  Change to dateToSeconds Function

  The dateToSeconds function includes a new parameter that 
  allows to you define which format to use when interpreting
  the date provided.  For more information, refer to the 
  XFDL Specification.
    
1.5.10  Scrolling Using the Mouse Wheel

  You can now scroll a form page by using the mouse wheel.
  
1.5.11  Support for printvisible Option

  The Viewer now supports the printvisible option.  This 
  option controls whether an item is visible or not when 
  the form is printed.  

  If you have relied on the global.global.activated option
  to turn item invisible during printing, you should update
  your forms to use the printvisible option instead.  The
  behavior of the global.global.activated option may change
  in future releases.

  For more information, refer to the XFDL Specification.
  
1.5.12  Support for printing Option

  The Viewer now supports the printing option.  This global 
  option indicates whether the Viewer is printing the form.  
  
  If you have relied on the global.global.activated option
  to determine when the form is printing, you should update
  your forms to use this new option.  The behavior of the 
  global.global.activated option may change in future 
  releases.
  
  For more information, refer to the XFDL Specification.
  
1.5.13  Support for New Viewer Settings (ufv_settings)

  The Viewer now supports the following ufv_settings:
  
  - savewithformaterrors - Controls the Viewer behavior if
        the user attempts to save a form that contains 
        formatting errors.

  - signwithformaterrors - Controls the Viewer behavior if
        the user attempts to sign a form that contains 
        formatting errors.

  - printwithformaterrors - Controls the Viewer behavior if
        the user attempts to print a form that contains 
        formatting errors.
        
  For more information, refer to the guide entitled, "Using
  Viewer Settings."

1.5.14  Support for Additional Screen Readers

  The Viewer now relies on the MSAA (Microsoft Active 
  Accessibility) standard to communicate with screen 
  readers.  This means the Viewer will work with any MSAA
  compliant screen reader.

1.5.15  Added Preferences Setting to Control Scroll Bars on 
        Zoomed Fields

  Version 6.0.1 introduced a feature that adds scroll bars
  to zoomed fields when they are required to allow the user
  to read the text in the field.
  
  This feature is now controlled by a setting in the 
  Viewer preferences, which allows you to turn the feature
  off.  However, the preferences setting can be 
  overridden by the ufv_setting for scrollfieldsonzoom.

1.5.16  Fixed Font Problem with Headers/Footers

  Fixed a problem that caused headers and footers to print
  with the wrong font.  They were using the font from the
  first item in the form rather than the default font.

1.5.17  Fixed Problem Printing Rich Text

  Fixed a problem that prevented rich text fields from 
  printing properly on some printers when the field was 
  large.

1.5.18  Changed Printsettings Default

  Changed the default value for the active setting in the
  printsettings option as follows:
  
  printsettings[dialog][printpages][active] now defaults 
  to "on".

1.5.19  Viewer Opens to Blank Form

  If you run the Viewer executable directly, the Viewer now 
  opens to display a blank form page rather than an "Open 
  Form" dialog box.  To open a form from the blank page, 
  simply click "Open Form" in the toolbar.

1.5.20  Changed Space Used By Tab Character

  The space used by a tab character is now controlled by the
  tab stops in a field.


------------------
1.6  Version 6.0.2
------------------

1.6.1  New Accessibility Feature for High Contrast Needs

  The Viewer now includes a feature that allows it to draw
  forms using the colors that are set for the operating 
  system rather than the colors set for the form.  This is 
  useful if the user has set the operating system colors to 
  offer better contrast or is using Microsoft Windows' High 
  Contrast mode.  Refer to the Viewer's User Manual for more 
  information.
  
1.6.2  colorinfo Option

  The Viewer now uses the colorinfo option in XFDL to record 
  the color settings in use when the user signs a form that 
  is drawn with operating system colors rather than those 
  colors defined in the form.  Refer to the XFDL 
  Specification for more information.
  
1.6.3  Fixed Duplicate Cells

  Fixed a problem that prevented newly created cells from 
  immediately showing up in the associated popups, combo 
  boxes, or list boxes.  This problem only affected version 
  6.0 forms. The Viewer now refreshes the list correctly so 
  that the cell shows up as soon as it is created.

1.6.4  Fixed SSL Submission Problem

  Fixed a problem that prevented large forms from submitting
  properly when using mutual authentication with SSL in the 
  stand-alone Viewer.
  
1.6.5  Does not Include Fix for Non-Scrolling Fields

  This version does not include the fix that was introduced
  in version 6.0.1 for non-scrolling fields.
  
1.6.6  Does not Include Fix for Zooming Fields

  This version does not include the fix that was introduced
  in version 6.0.1 for zooming fields.
  
------------------
1.7  Version 6.0.1
------------------

1.7.1  Support For Additional Fonts

  The Viewer now supports the CG Times and Univers fonts
  for plain text items only.  To use these fonts, use the 
  font names "CG Times" or "Univers" in the fontinfo option 
  and use the "Central European (ISO)" character set.

1.7.2  Fixed Input Problem with Non-Scrolling Fields

  Corrected a problem that prevented fields with a 
  scrollvert setting of "fixed" from accepting the correct 
  number of lines of input.

1.7.3  Fixed a Problem with Zooming Fields

  In some cases, zooming a multi-line field with scrollvert 
  of "fixed" or a single line field with a scrollhoriz of 
  "wordwrap" results in the text sizing incorrectly.  This 
  can cause some of the text to disappear beyond the edge or 
  bottom of the field.
  
  This prevents users from reading the complete text in 
  the field and from entering as much text as should be 
  allowed.
  
  To correct this for multi-line, fixed height fields, 
  vertical scrollbars are now automatically added when 
  needed.  To correct this for single line, wordwrap fields, 
  the field now allows horizontal scrolling (with no 
  scrollbars) when necessary.  In both cases, users can 
  enter the exact amount of text the field would allow at
  100% zoom factor, and can read all of the text in the 
  field.
  
  This behavior is controlled by a new ufv_setting called
  "scrollfieldsonzoom", and defaults to "on", which 
  provides the scrollbars.  For more information on this 
  setting, refer to the guide entitled, "Using Viewer 
  Settings".
  
  Note:  This functionality was changed in version 6.1.
  Refer to version 6.1 section for more information.

------------------
1.8  Version 6.0.0
------------------

-------------------
1.8.1  XFDL Changes
-------------------

  The Viewer implements all of the XFDL changes listed in 
  this section.

1.8.1.1  Namespace Support

  Namespace support has been added to the XFDL language for 
  XFDL documents version 6.0 and higher. Note that:

  - The XFDL namespace URL is: 
      http://www.PureEdge.com/XFDL/6.0
  - The XFDL namespace is the default namespace for the 
    document. 
  - All non-XFDL elements must have their own namespace.
  - You must declare the default namespace, xfdl namespace, 
    and any custom namespaces at the beginning of your XFDL 
    form, immediately following the <?xml version="x.x"?> 
    tag.

  For example:

     <XFDL xmlns="http://www.PureEdge.com/XFDL/6.0" 
       xmlns:xfdl="http://www.PureEdge.com/XFDL/6.0" 
       xmlns:custom="http://www.PureEdge.com/XFDL/Custom">

1.8.1.2  Defining a Form's Version

  With the introduction of namespace support, a form's 
  XFDL version is now defined by the namespace used for the
  XFDL element.  For example, a version 6.0 form will 
  include the following XFDL tag:
  
  <XFDL xmlns="http://www.PureEdge.com/XFDL/6.0"
  
  However, you can still reference a form's version as 
  though it were a global option, as shown:
  
  global.global.version

1.8.1.3  XML Data Model

  XFDL now supports an XML Data Model.  This model allows
  form designers to create separate blocks of arbitrary 
  XML within an XFDL form that share data with form 
  elements, such as fields.  This is useful for integrating 
  with applications that require data in a particular XML 
  format, such as schema-compliant data.  The XML Data Model 
  is based on the XForms standard, as published by the W3C, 
  but is not limited to XForms.  Refer to the XFDL 
  Specification for more information.

1.8.1.4  XFDL Computes 

  XFDL computes are now attributes of the option tag. As a 
  result, computes are contained in the opening tag of the 
  option, and the current value of the compute is stored as 
  simple character data in the option. The compute itself is 
  enclosed by quotes.  For example:

  <field sid="FIELD1">
    <value compute="PAGE1.nameField.value"
      >Jane E. Smith</value>
  </field>
  
  Additionally, because computes are now enclosed in 
  quotation marks ("), elements of the compute that used to 
  be enclosed in quotations marks, such as strings, are now 
  enclosed by apostrophes ('). For example, in the following 
  compute the value 10 is enclosed in apostrophes:
  
  <value compute="PAGE1.amountField.value + '10'"></value>

1.8.1.5  Namespaces in If/Then/Else Computes

  If you are using an if/then/else compute that contains a 
  namespace in the "then" portion, you must enclose the 
  "then" portion in parentheses, as follows: 
  
    x ? (y) : z  
  
  For example:
  
    FIELD1.value == '10' ? (FIELD1.custom:myOption) :
      FIELD2.value
  
  If you do not enclose the "then" portion in parentheses, 
  the parser will mistake the colon following the namespace 
  prefix as the end of the "then" portion, and the compute 
  will not function properly.

1.8.1.6  Multiline Computes

  To place computes on multiple lines for easier 
  readability, you must place a new line entity reference 
  wherever you want to break a line.  The new line entity 
  reference is &#xA;

  For example:
 	
     <custom:my_opt xfdl:compute = "toggle(activated, &#xA;
       'off',  'on') == '1' ? &#xA;
       set('convertedDate.value', &#xA; 
       sample_package.convertDate(theDate.value, &#xA;
       theLocale.value)) : ''"></custom:my_opt>

1.8.1.7  Supported Characters for Sid and Element Names

  XFDL 6.0 supports the following Unicode characters in 
  sid and element names (hex notation in parentheses):
  
  0-9 (30 to 39)
  A-Z (41 to 5A)
  a-z (61 to 7A)
  _ (5F)
  (B7)
  (C0 to D6)
  (D8 to F6)
  (F8 to FF)
  
  Sid and element names cannot start with:
  
  0-9 (30 to 39)
  (B7)

  Note that the $ character is no longer allowed, and 
  that the _ (underscore) character is no longer mandatory 
  in custom item/option names.

1.8.1.8  Escaped Characters

  You must escape the ampersand (&), apostrophe ('), and 
  less than sign (<) to use these characters in computes or 
  as character data.

  To escape these characters, use the following encoding:
  & - &amp;
  ' - &apos;
  < - &lt;

1.8.1.9  New Reserved Words ('or' and 'and')

  'and' and 'or' have been added to the XFDL language as 
  reserved words. They represent logical AND (&&) and 
  logical OR (||), respectively.

1.8.1.10  Arrays

  Options containing arrays no longer need to include the 
  content="array" attribute within the option tag. For
  example, you would now write an itemlocation option as:

	<itemlocation>
             <ae> 
		<ae>absolute</ae>
		<ae>276</ae>
		<ae>66</ae>
	     </ae>
	     <ae>
		<ae>extent</ae>
		<ae>246</ae>
		<ae>56</ae>
	     </ae>
	</itemlocation>

1.8.1.11  Additional Character Set Support

  XFDL now supports multiple character sets for fonts, as 
  specified by the fontinfo option.  For more information,
  refer to the XFDL 6.0 Specification. 

1.8.1.12  MIME Type For Forms

  The application/x-xfdl MIME type is deprecated.  All 
  forms and applications should use the application/vnd.xfdl
  MIME type instead.
  
  Support for the application/x-xfdl MIME type may be 
  dropped in future versions.

1.8.1.13  Explicit Global Page and Global Items

  XFDL now declares explicit global page and global 
  items.  The global page is marked with the "globalpage" 
  tag, and global items are marked with the "global" tag.  
  Both global pages and global items must have a sid of 
  "global".  For example:
  
  <?xml version="1.0"?>
  <XFDL xmlns="http://www.PureEdge.com/XFDL/6.0"
  	xmlns:xfdl="http://www.PureEdge.com/XFDL/6.0"
	<globalpage sid="global>
  		<global sid="global">
  			...global form settings...
  		</global>
  	</globalpage>
  	<page sid="Page1">
  		<global sid="global">
  			...global page settings...
  		</global>
  		...page contents...
  	</page>
  </XFDL>
  
  For more information, refer to the XFDL 6.0 Specification.

1.8.1.14  New XFDL Function Calls

  XFDL now supports the following function calls:
  
  countDatagroupItems - Allows you to count the total number
      of items in a particular datagroup.
  
  countGroupedItems - Allows you to count the total number
      of items in a particular group.

  getAttr - Allows you to get the value of an attribute on
      any element in a form.
  
  getPosition - Allows you to get the position index of an
      element within its parent.
  
  getPref - Allows you to get the value of any setting in 
      Viewer Preferences form.
      
  getGroupedItem - Allows you to get the SID (scope 
      identifier) of an item in a particular group.
      
  setAttr - Allows you to set the value of an attribute
      on any element in a form.
      
  xmlmodelUpdate - Allows you to update the XML Data Model 
      in memory. This is useful if you have made 
      computational changes to the data model.      
      
  For more information about these functions, refer to the 
  XFDL Specification.
  
1.8.1.15  Change to Default Type for Actions and Buttons

  Action and button items now default to a type of select.
  
1.8.1.16  New Encoding Attribute and Encoding Method

  Options and array elements now support an encoding 
  attribute that defines the encoding method used for the 
  tag's contents.  For example:
  
  <mimedata encoding="base64"></mimedata>
  
  Valid encoding methods are:
  - xml
  - base64
  - base64-gzip
  
  Note that base64-gzip is a new encoding method that 
  gzips the contents and then converts them to base64.
  
  The default encoding is xml, and all MIME data is 
  stored in base64-gzip format. 
  
  Refer to the XFDL Specification for more information.
  
1.8.1.17  Support for Rich Text Fields

  XFDL now supports rich text fields.  These are enabled 
  through the following new options:
  - rtf
  - texttype
  
  Refer to the XFDL Specification for more information about
  the new options.

1.8.1.18  Default Display Value for Popup Items

  If a popup does not have a label or a value option, it 
  will be blank.  Formerly, the popup displayed the value 
  of the first cell.

1.8.1.19  Parent Operator for References

  XFDL now supports a double dot (..) parent operator for 
  references. The parent operator must appear at the 
  beginning of a reference, and can appear multiple times 
  to indicate additional ancestors. For example, the 
  following are now valid references:
  
  ..FIELD1.value
  ....value
  
  The first reference gets the parent of the current node, 
  then locates the Field1 node, then the value node. The 
  second gets the parent of the current node, then the 
  parent of that node, then locates the value node.
  
  Refer to the XFDL Specification for more information.

1.8.1.20  New Sign and Transmit Filters for Namespaces

  XFDL supports two new filtering options: signnamespaces 
  and transmitnamespaces.  These options allow you to filter 
  which namespaces are included in signatures and 
  transmissions.
  
  Refer to the XFDL specification for more information.

----------------------
1.8.2  Viewer Features
----------------------

1.8.2.1  Support for XFDL 6.0

  The Viewer now supports XFDL 6.0 forms.

1.8.2.2  Support for Netscape 7

  The Viewer now supports Netscape 7.

1.8.2.3  Dropped Support for UFDL

  PureEdge Viewer no longer supports the Universal Forms 
  Description Language (UFDL).  Furthermore, files with
  a .ufd or .ufdl extension are no longer recognized and 
  the application/vnd.ufdl MIME type is no longer supported.

1.8.2.4  Deprecated .frm File Extension

  The .frm file extension has been deprecated.  All new
  forms should use the .xfd or .xfdl file extension.
  
  Support for the .frm file extension may be dropped in
  future versions.

1.8.2.5  Backwards Compatibility
  
  PureEdge Viewer 6.1 supports XFDL version 4.4 and later. 
  If a form of a version earlier than 4.4 is opened, the 
  Viewer will process it as a version 4.4 form, and will 
  apply the version 4.4 rules to the form.

  Furthermore, PureEdge Viewer 6.1 is compatible with 
  extensions (.ifx files) compiled with the version 4.5 
  API or later.  Extensions compiled with earlier versions 
  of the API will not work with this version of the Viewer.

1.8.2.6  Serialization of URLs in the url Option

  If you list multiple URLs in the url option, the URLs 
  are now processed in the order listed (formerly the 
  order was undetermined).
  
  For example, if a button of type submit listed 2 URLs, 
  the submission would process the first URL and then the
  second URL.
  
  However, if an action occurs that replaces or closes the 
  original form (for example, a replace or done action) no 
  further URLs are processed.
  
  For example, if a button of type done listed 2 URLs, the
  submission would process the first URL then close the 
  original form, preventing the second URL from being 
  processed.
  
1.8.2.7  Removed Open File Shortcut

  The Viewer no longer supports the ALT-CTRL-F key sequence
  for opening new files.
  
1.8.2.8  Character Set Support

  The Viewer now supports multiple character sets for fonts, 
  as specified by the fontinfo option.  For more information,
  refer to the XFDL 6.0 Specification. 

1.8.2.9  Activating the Screen Reader

  The screen reader is no longer activated through a 
  selection in the Viewer Preferences.  Instead, the Viewer 
  always makes screen reader information available.  If JAWS
  is active, it will automatically recognize and read this 
  information.

1.8.2.10  MAPI Support On By Default

  The Viewer now defaults to using the active MAPI client 
  when sending email.  If you do not have a MAPI client
  available, you can change this setting in the Viewer
  Preferences.
  
1.8.2.11  New Zoom Feature

  The Viewer now supports the ability to zoom forms 
  from 25% to 200% of normal size.  This feature is 
  controlled by buttons on the Viewer's toolbar. Refer 
  to the PureEdge Viewer User's Manual for more information.
  
1.8.2.12  Sizing of Items with label Options

  Items for which the label option is set, but that have 
  no border on the label, are now two pixels taller.  
  This additional height accounts for the space the border
  would use if it were there.  This may affect the spacing
  of items on any form that you upgrade to version 6.0.

1.8.2.13  Updated Shortcut Keys

  The following shortcut keys have been changed:
  
  CTRL + I   No longer opens the about dialog. It now 
             toggles italics in rich text fields.
           
  The following shortcut keys have been added:
  
  CTRL + B           Toggles bold in rich text fields.
  
  CTRL + F           Opens the Font dialog, which allows
                     you to adjust font properties in rich
                     text fields.
                     
  CTRL + G           Opens the Paragraph dialog, which 
                     allows you to adjust indent and 
                     justification in rich text fields.
                     
  CTRL + U           Toggles underline in rich text fields.
  
  CTRL + R           Right justifies text in rich text 
                     fields.
  
  CTRL + SHIFT +     Increases the zoom (magnification) of 
  PLUS               the form.
                     
  CTRL + MINUS       Decreases the zoom (magnification) of 
                     the form.
                     
  CTRL + SHIFT + ?   Opens the about dialog.

1.8.2.14  Updated toggle Function

  The implementation of the toggle function has been updated 
  for version 6.0 forms to resolve outstanding problems.  
  This may affect some forms that rely on unusual behavior.  
  Be sure to test all forms that rely on the toggle function
  if you upgrade them to version 6.0.

1.8.2.15  Changed Default Height for Extent

  Previously, if you did not provide a height for an extent
  (for example, if you used a compute to calculate the 
  height but did not provide a starting value) the height
  would default to equal the width.
  
  The height will now default to zero if no initial value
  is provided.  This may impact forms that have expanding 
  fields.  If you want to recreate the old behavior, 
  simply provide an initial value for the height.

1.8.2.16  Added New ufv_settings

  The Viewer now supports the following new ufv_settings:
  
  aboutboxtext - Allows you add information to the Viewer's 
    about box.  This is useful if you want to add contact 
    information, such as a name, address, and phone number.
    
  helpcursor - Allows you to control the appearance of the
    pointer when the Viewer is in help mode.
    
  For more information, refer to the Using the Viewer 
  Settings document available on the documentation web site.

1.8.2.17  Copying IFX Extensions from Older Viewers

  The Viewer no longer copies IFX extension files from 
  older versions of the Viewer during installation.  You 
  must copy these files manually.
  
1.8.2.18  Buttons and Labels with Empty Images

  If a button or label's image option points to a data 
  item that is empty or does not exist, then the button
  or label will display its value option instead. Formerly,
  the button or label displayed nothing.
    
------------------------------------
1.9  Version 5.2.0 (Limited Release)
------------------------------------

1.9.1  Support for Verifier Flag in signformat Option

  The Viewer now supports a verifier flag in the 
  signformat option.  This flag controls the level of 
  rigor applied when verifying certificates.  For more 
  information, refer to the XFDL Specification.
  
1.9.2  User Preferences No Longer Copied During Upgrade

  The Viewer no longer copies existing user preferences 
  when upgrading from a previous version.  If you are 
  upgrading your installation of PureEdge Viewer, be sure
  to reset your user preferences manually.

1.9.3  Fixed Problem Opening Forms with IE6 Under Windows XP

  Fixed a problem with IE6 under Windows XP that caused 
  forms to open in standalone mode rather than in the 
  browser.
  
1.9.4  Fixed Wildcards for Certificate Filtering in 
       signdetails Option
       
  Fixed a problem that prevented wildcards from functioning
  properly when used in the signdetails option to control
  certificate filtering.
  
1.9.5  Dropped Windows 95 Support

  Windows 95 is no longer supported and the Viewer is no 
  longer tested in this environment.

-------------------
1.10  Version 5.1.1
-------------------

1.10.1  Change to 'X' Style Check Boxes

  X Style check boxes now adjust the thickness of the X
  according to the size of the check box.  This results
  in a thicker and more noticeable X as the size of the 
  check box increases.

-------------------
1.11  Version 5.1.0
-------------------

1.11.1  Running the Viewer as a User

  You can now run the Viewer as a regular User under 
  Windows (rather than as an Administrator or Power User).

1.11.2  User Profiles

  The Viewer now respects user profiles under Windows.  The 
  Viewer must be installed using an Administrator profile, 
  but is then managed and licensed through individual user 
  profiles.  Refer to the installation and licensing 
  sections of the Viewer User's Manual for more information.
  
  Note that roaming profiles are not supported.
  
1.11.3  Network Access

  Previous versions of the Viewer included two network 
  access modes: online and offline.  The Viewer now supports 
  the following four modes:
  
  - online:  user is online.
  - online with backup:  user is online and a backup 
        copy of the last form submitted is retained.
  - offline:  user is offline and is prompted to save
        forms rather than submitting them.
  - offline with archiving:  user is offline and the Viewer
        automatically archives submitted forms.

  The Network Access is set in the Viewer's Basic 
  Preferences.  Refer to the Viewer User's Manual for more
  information.

1.11.4  Help Mode

  The Viewer's Help Mode now applies to the entire form,
  rather than just the current page.  When the user 
  switches to a different page, the Help Mode will remain
  on (rather than turning off as it used to).
  
1.11.5  Authenticated Clickwrap
  
  The Viewer now supports an additional version of the 
  Clickwrap signature, called Authenticated Clickwrap.
  Authenticated Clickwrap uses a shared secret (such as
  a password known to both the user and the company)
  to provide further proof of the signer's identity.
  
  The shared secret is entered when the user signs the form, 
  but is not actually stored in the form.  Instead, it is 
  securely combined with the document content to form a 
  token that server-side components can verify using 
  PureEdge API and the shared secret.  This requires a 
  database (or other application) that maintains a list of 
  users and secrets.

  Once the server-side component has verified the signature, 
  it can optionally add a notarizing digital signature to 
  the form, so that other client-side users can authenticate 
  the signer based on trust of the server's notarizing 
  signature.
  
  Authenticated Clickwrap signatures are inherently more 
  secure than Clickwrap signatures, and therefore the 
  Viewer applies overlap and layout testing.

  Note that Clickwrap signatures are still supported, but 
  that overlap and layout testing is not performed on them.
  
  For more information on creating a system that supports 
  Authenticated Clickwrap signatures, refer to the 
  "Implementing Authenticated Clickwrap" document available
  from the PureEdge website (docs.PureEdge.com).
  
1.11.6  Sizing Check Boxes and Radio Buttons using Extent

  Fixed a bug that prevented check boxes and radio buttons
  from properly respecting horizontal extent settings that
  were less than the width of a box as defined by the font
  height.
  
1.11.7  Linespacing Option

  Buttons, labels, and spacers now support the linespacing
  option.  This option adjusts the space between lines of 
  text, either increasing or decreasing the space depending
  on the setting.  Refer to the XFDL Specification for more 
  information.
  
1.11.8  Sizing Field Items

  When drawing a field that is sized using the size option, 
  the Viewer no longer includes the external font leading in
  the character height.  This means that some fields will 
  appear smaller.  The measureHeight function will also 
  account for this change. 
  
  Note that this change is controlled by the form version 
  and applies only to version 5.1 and later forms.  All 
  other items that contain text (such as buttons and labels) 
  respect font leading at all times.
    
1.11.9  Copying and Pasting Text

  In some cases, when you copy text to the Windows clipboard 
  a trailing new line marker is included (for example, when 
  copying text from MS Word).  This marker causes pastes to 
  fields with a fixed height to fail.  The Viewer now 
  detects a failure and tries again after removing a 
  trailing new line marker.
  
1.11.10  Controlling the Viewer's Toolbar

  Added the ability to remove buttons from the Viewer's 
  toolbar.  Previously, you could only make the buttons
  inactive.  This is done using the ufv_settings option.
  
1.11.11  Input Military Time

  Fields set to a time format will now accept three or 
  four digit 'military time'.  For example, 600, 0600, 
  and 2300 are all valid inputs.


================
2.  KNOWN ISSUES
================

----------
2.1  Users
----------

2.1.1  Setting Computes for Fields

  You cannot use computes to set the justify option or to 
  set an editstate of writeonly.
   
2.1.2  Using Eudora or Netscape as MAPI Client for the 
       Viewer

  If you want to use Netscape Messenger or Eudora as the 
  Viewer's e-mail program, you will first need to turn on 
  MAPI support in these applications. However, this option 
  is not available in Netscape versions prior to 4.5 or in 
  version 6.1. 

  To enable MAPI support:

  In Netscape, go to Preferences > Mail & News Groups 
  settings.

  In Eudora, go to Options > MAPI settings.

  You then need to set PureEdge Viewer's preferences. Go to 
  the Viewer Preferences form and select "Use Default Simple 
  MAPI Client" under "Mail Configuration" in Basic settings.

2.1.3  Text Fields

  Text fields that the Viewer displays can support up to 
  500K of text. If you try to insert more than 500K of text 
  (about 7,500 lines in a 60-character wide field), the text 
  will be truncated at the 500K mark.

2.1.4  Moving Back and Forward in a Web Browser

  If you start to fill out a form while using the Viewer in 
  a browser, then open a new web page or file in the same 
  browser window, you will lose the information you have 
  entered into the form.

2.1.5  Giving the Focus to Input Items that Overlap Labels

  When input items (such as fields, buttons, popups, lists, 
  comboboxes, radios, and check boxes) are placed on top of 
  labels, you cannot use the mouse to give the items the 
  focus or to interact with the item (for example, you 
  cannot click a check box to turn it on or off).  You must 
  use the TAB key to move to the item and the keyboard to 
  enter information in the item.

2.1.6  Installing Viewer 6.5 with ICS Designer 2.0 or 
       Earlier

  If you install Viewer 6.5 on the same computer as ICS 
  Designer 2.0 or earlier, you may receive warning messages
  when you open the Designer.  Viewer 6.5 installs updated 
  .ifx files that older versions of the Designer cannot 
  process properly.  If you encounter this problem, upgrade 
  the Designer to version 6.5.

2.1.7  Standalone Viewer and Netscape 6.x

  When running in standalone mode, the Viewer cannot use 
  Netscape 6.x for communications.  Instead, it will default
  to using the WinINet communications libraries that are 
  installed with Windows.  This has two effects:
  
  1.  When any non-XFDL document is returned, the Viewer
      will not be able to open Netscape 6.x to display
      that document.  Instead, the document will open in 
      either Internet Explorer or an earlier version of 
      Netscape, if they are available.

  2.  SSL certificates installed in Netscape are not 
      available to the Viewer.  To correct this problem, 
      either ensure that the Viewer is running within the 
      browser (as a plugin) or ensure that your SSL 
      certificates are installed in IE.
      
2.1.8  Accessing the Netscape Certificate Store

  The Viewer will only access the certificate store in the 
  most recent version of Netscape installed on your 
  computer.  If you install a certificate in an earlier 
  version of Netscape, and have a later version installed, 
  the Viewer will not be able to access that certificate.
  
  To correct this, ensure that all of your certificates are
  installed in the latest supported version of Netscape that 
  is on your computer.
  
2.1.9  Viewing Forms in IE 5, 5.01, 5.01 SP1, 5.5, 5.5 SP1
        
  When you open a form from a web site, you may receive 
  an error message (such as "The page cannot be displayed") 
  instead of viewing the form.  This happens because the 
  Active Document Server is looking for a cached copy of 
  the form and cannot find one.  You can still open the form 
  by refreshing the browser (click the refresh button).
  
  To fix this on the server, you will need to remove any 
  cache control information from the HTTP headers.  For 
  more information, refer to the following Microsoft 
  Knowledge Base article:  Q297822.

2.1.10  Using the Keyboard to Move the Focus from the
        Address Bar in Netscape
        
  Under Netscape 6.0 or later, you can normally press the 
  TAB key twice to move from the address bar to the contents 
  of the browser (in this case, to the form).  However, when 
  using a plugin, Netscape will generate an application 
  error rather than move the focus to the document. 
  
  Under Netscape 4.x, there is no keyboard support for 
  moving the focus from the address bar.
  
  For these reasons, we suggest you use Internet Explorer
  rather than Netscape if you are using screen reader mode 
  and must rely on keyboard controls.
  
2.1.11  Underlined Text on Buttons when in Screen Reader 
        Mode
        
  If you are using JAWS, JAWS will mistakenly report any 
  button that displays underlined text as a hotkey.  JAWS 
  always reports the hotkey as an 'ALT' combination with 
  the first letter of the underlined text.  For example, 
  a button that read "Click me" in underlined text would 
  be reported as having an 'ALT + C' hotkey.  The hotkey 
  is not actually available in these cases.
  
2.1.12  SSL Submissions Under Internet Explorer 5 and 5.5

  Under IE 5 and 5.5, the submission of a form using SSL 
  will fail if the browser presents any SSL related dialog
  box.  This is primarily of concern when the browser 
  presents a dialog requesting that the user choose an SSL 
  identity (that is, a certificate).  This is due to a bug 
  in the IE browser's IWebBrowser2 interface, and has been 
  fixed in IE6.
  
  Once you have selected an SSL identity, subsequent 
  submissions will work properly.
  
  For a recommended solution, see section 2.2.

2.1.13  Using Netscape Browsers under Windows XP

  Use Netscape 6.23 or greater under Windows XP.  Earlier
  versions of Netscape will exhibit problems when drawing
  the form (this problem is common to other applications).

2.1.14  Running the Viewer Under Another User Profile

  You can only run the Viewer under the current user 
  profile.  For example, the Windows "Run as..." feature 
  will not work.

2.1.15  Conflicting MAPI Clients under Windows XP

  If you have both Microsoft Outlook and Netscape Mail 
  installed under Windows XP, ensure that only one of the 
  mail clients is set to make itself the default client.  If 
  both clients are set to make themselves the default client 
  when run, you may experience problems.
  
2.1.16  Printing Rich Text Fields Causes Wordwrap

  If you have text in an Rich Text field that extends past 
  the end of the field, this text will be wordwrapped when 
  you print the form. This occurs regardless of how the 
  scrollhoriz option is set for the field.

2.1.17  Help Not Shown For Inactive Items

  Help messages are not shown for inactive items, with the 
  exception of fields and comboboxes.  This affects help
  messages displayed for signed items as well as those 
  displayed when in Help Mode.
  
2.1.18  Appearance of Fonts when Zooming

  Some fonts do not scale well when zooming the form, which 
  may cause text to appear cut off in some fields.  This 
  problem is most noticeable in fields that are either very
  small or very large.  To correct this problem, use 100% 
  zoom factor to view the form.

---------------
2.2  Developers
---------------
  
2.2.1  Limitations on Computes and Set

  Radio button values cannot contain a compute. However, 
  they can be modified by the "set" function, and you can 
  reference radio button values in computes for other 
  options.
  
  Computes cannot be used to set the justify option of 
  fields and comboboxes.  Set cannot be used to do this 
  either.
  
  Computes cannot be used to set the editstate of fields 
  and comboboxes to be "writeonly".  Set cannot be used to 
  do this either.
  
2.2.2  Using the Set Function Call with Radio Buttons

  If using a Set function to set the on/off values for radio
  buttons, it is possible to destroy the functionality of 
  the radio button's group option. To avoid this, set all 
  radio buttons in a particular group at the same time. For 
  example, if you use a Set function to turn a radio on, 
  make sure you use a set function to turn each of the 
  other radio buttons off. 
        
2.2.3  Web Browsers and "Cancelled" Forms

  Because of the nature of web browsers, a user can always 
  return to a cancelled form. For example, if you give a 
  button a type of "done", the form will perform a 
  submission and then cancel itself. However, in a web 
  browser, a user can click the Back button to return to 
  the form.

2.2.4  Corrupted Image Data

  Opening a form that contains corrupted image data may 
  cause the Viewer to crash.

2.2.5  JPEG Support

  PureEdge Viewer supports Standard JPEG image formats. If 
  your image is a Progressive JPEG you will need to open it 
  in a graphics program and save it as a Standard JPEG.
  
2.2.6  Using the Destroy Function

  The destroy function cannot delete the item that triggered
  the destroy.  For example, if clicking a button calls the 
  destroy function, the function cannot destroy the button 
  itself.
  
  Additionally, you cannot use the XFDL destroy function to 
  remove a spacer from the form.  If you attempt to do this, 
  the Viewer will not destroy the spacer and will display an
  error.

2.2.7  Using Email Parameters in the URL Option Under 
       Netscape 6.2 or 7.x

  Normally, if you include all email parameters (email 
  address, cc, bcc, subject, and body) in a URL option, 
  the Viewer will send the email without showing the user
  an email dialog.  However, due to bugs in Netscape, this 
  does not work properly.
  
  Netscape 6.2 will return an error when the user tries
  to mail the form, and will not send the email.
  
  Netscape 7.x will not send the email and will not inform
  the user of a problem.
  
  To avoid this problem, leave at least one email parameter
  out of the URL option.

2.2.8  SSL Submissions Under Internet Explorer 5 and 5.5

  Under IE 5 and 5.5, the submission of a form using SSL 
  will fail if the browser presents any SSL related dialog
  box.  This is primarily of concern when the browser 
  presents a dialog requesting that the user choose an SSL 
  identity (that is, a certificate).  This is due to a bug 
  in the IE browser's IWebBrowser2 interface, and has been 
  fixed in IE6.
  
  If your users are going to perform submissions using SSL 
  under IE5 or 5.5, we recommend that you implement an HTML 
  page that requires SSL authentication, and that users must 
  view before opening a form.  This forces the selection of 
  the user's SSL identity.  Once the SSL identity is 
  selected, the browser will not present the selection 
  dialog box again, and SSL submissions will succeed.
  
  Note that users who protect their certificates with a 
  password may still need to enter that password, but that
  this will not prevent a successful submission.
  
2.2.9  addressBook Function Under Netscape 6.x and 7.x

  Netscape version 6.x and 7.x does not properly support 
  the MAPI address book (accessed using the addressBook 
  function).  The user will receive an error message if 
  they try to open the address book under these versions 
  of Netscape.

2.2.10  Mailto URLs Under Netscape 6.x

  Forms with mailto URLs will fail to send under Netscape 
  6.x if the URL contains both the recipient and the body 
  of the message.  Netscape will produce an error message 
  and will fail to send the form.  Adding additional 
  parameters to the URL will not affect this behavior.

2.2.11  Label Options in Fields not Redrawn Properly

  If a field's label option is empty and you set the label
  option dynamically (with a compute), the field is not 
  redrawn properly.

2.2.12  activated Option when Closing a Form

  When you close a form, the activated option for the
  form and any page in the form (that is 
  global.global.activated and page.global.activated) do not 
  turn off before the form closes.

2.2.13  Signing Items with Small Fonts

  Signing items with fonts that are 5 points or smaller in
  size may cause the signature to break across different
  versions of Windows.
  
  The Viewer uses the Windows "Small Font" when displaying
  any fonts that are 5 points or smaller in size.  The 
  metrics used to display the Small Font change across 
  different versions of Windows, and may result in slightly 
  larger or smaller text depending on the operating system.
  
  If your items are sized by character size or if they 
  default to the length of the text, this may result in 
  slightly larger or smaller items, which will cause the 
  layout test to fail when validating a signature.

  To correct this problem, ensure that all items using small
  fonts are sized using the extent setting in the 
  itemlocation option.  This will size the item based on 
  the pixel size rather than character size, ensures the 
  items do not change their size based on the font in use.

2.2.14  Signing Items with Uncommon Fonts

  Signing items with fonts that are not generally available
  may cause the signature to break across different 
  computers.

  If the font is not available on the current computer, 
  Windows will substitute a different font that may not
  be exactly the same size.
  
  If your items are sized by character size or if they 
  default to the length of the text, this may result in
  slightly larger or smaller items, which will cause the 
  layout test to fail when validating a signature.
  
  To correct this problem, ensure that all items using 
  uncommon fonts are sized using the extent setting in 
  the itemlocation option.  This will size the item based 
  on the pixel size rather than character size, ensures the 
  items do not change their size based on the font in use.

2.2.15  Dynamically Changing RTF Fields to Plain Text

  The Viewer does not support dynamically changing RTF 
  fields to plain text.  Attempting to do so may result
  in unexpected behavior.

2.2.16  Background Color Does Not Print Properly for Rich
        Text Fields

  When printing rich text fields, background colors will not 
  print properly.  To solve this problem, you should set 
  rich text fields to have a printbgcolor option of white.

  If you are using Rich Text fields as labels and want
  them to match the background color of the form, consider
  printing the entire form with a white background.  This 
  will print a clean looking form and will save toner.

2.2.17  Using Rich Text in Fixed Size Fields

  Do not use rich text in fixed size fields.  Rich text does 
  not support the level of precision required to properly 
  limit the text within the constraints of the field.  In 
  many cases, formatting and printing will cause the text 
  to extend beyond the boundaries of the field.

2.2.18  Printing Rich Text Fields

  Rich text fields do not support a high level of precision
  when printing.  This means that the text may look different
  or wrap differently when printed.

2.2.19  Using F1 and F6 as Keypress Events

  Do not use F1 or F6 as keypress events.  When the Viewer
  is running in a web browser, the browser interferes with
  capturing these events.
  
2.2.20  Verifying Signatures in Older Forms

  This version of the Viewer may not be able to verify 
  signatures in older forms.  This issue is specific to 
  forms of version 4.4 or older that were signed in Viewer 
  6.0 or 6.1.  

====================
3. OTHER USAGE NOTES
====================

3.1  Application/X-XFDL MIME type

  The use of the x-xfdl MIME type is no longer recommended.
  However, this version of the Viewer continues to support 
  this MIME type to maintain backward compatibility with 
  older forms.  Use the application/vnd.xfdl MIME type 
  instead.

3.2  Windows 2000/XP

  To install the Viewer under Windows 2000/XP, you must be 
  logged onto Windows as an Administrator.

3.3  Printing   

  PureEdge Viewer prints the body of the form, including 
  the form itself and all information in the form.  However, 
  the Viewer does not print the toolbar of the form, nor can 
  it print only the data entered into the form.

3.4  Form Errors

  PureEdge Viewer refuses to display some forms containing
  "fatal" form design errors.  These are generally errors 
  that could seriously affect the form's appearance or 
  functionality.

3.5  Available Digital Certificates

  When signing a form in Internet Explorer under Windows 
  98, you may find that all of the digital certificates 
  on the computer are listed as being available, regardless 
  of which user is trying to sign.  To change it so that 
  only the current user's certificates are listed when 
  signing a form:
  
  1.  From the Start menu, point to Settings, and choose 
      Control Panel.
      
  2.  Double-click the Passwords icon.
  
  3.  Select the User Profiles tab.
  
  4.  Choose the radio button that allows users to customize 
      their settings.
      
  5.  Click OK.

3.6  Supported Virtual Machines

  When using Java, the Viewer supports the Sun Java Virtual 
  Machine version 1.2 or later.
    
3.7  Using Boxes to Frame Other Items

  Boxes are automatically drawn in the background regardless 
  of their position in the XFDL build order.  This means 
  that items framed by a box will be visible and will 
  function properly even if they come after the box in the 
  build order.

3.8  Scaling a Form that Uses Header/Footer Functions

  When you use "Shrink to Page" to shrink a form when 
  printing, the Viewer will also shrink any headers or 
  footers you have added to the form.  This generally
  produces a perfectly readable print.

  However, if you use "Fit to Page" to make the form larger
  when printing, the headers/footers are also made larger.  
  This generally does not produce a readable result, as the 
  header is usually truncated and the footer usually 
  disappears altogether.

3.9  Temporary Files Created when Using the Viewer

  In normal operation of the Viewer, your web browser will 
  create a number of temporary files.  These temporary files
  are outside the control of the Viewer, and are managed
  by your web browser.
  
  The files are normally deleted immediately, using standard 
  deletion calls.  However, scans with a memory tool (for 
  example, a hex scan) will still detect the deleted files.
  
  When a form is sent via email, the temporary file must
  be available to the email client, and therefore is not
  deleted immediately.  However, the file is deleted 
  the next time the computer is rebooted.

==================
4. TROUBLESHOOTING
==================

-----------------
4.1  Installation
-----------------

4.1.1  Unrecognized MIME Type Error Message When Viewing
       Forms in a Web Browser

  If you receive an error message announcing an unrecognized 
  MIME type when you try to open a form in a web browser, 
  then your web browser is unable to find PureEdge Viewer. 
  This may be because the setup program was unable to find 
  the web browser during installation.
 
  To fix this problem, you will have to setup the Viewer
  manually.  Refer to the "Installation Notes" section in
  the readme_en_US.txt file for more information. 

4.1.2  Viewer Launching As Stand-alone Application

  If your forms are opening in a stand-alone PureEdge 
  Viewer, instead of in the browser window, then the setup 
  program was unable to automatically install the browser 
  extension in your web browser's plugins directory.
  
  To fix this problem, you will have to setup the Viewer
  manually.  Refer to the "Installation Notes" section in
  the readme_en_US.txt file for more information.

4.1.3  .xfd File Extension Not Mapped Properly

  PureEdge customers using Adobe Acrobat Reader 6.0 may 
  encounter problems related to the use of the .xfd file 
  extension. Some versions of Adobe 6.0 register the .xfd 
  file extension. This may cause a problem if the Adobe 
  product is installed after the PureEdge software. 
  
  To correct this problem, you can do either of the 
  following:
  
  - Uninstall then re-install the Viewer. This fixes
    the problem, but it may return at a later date 
    depending on your use of Adobe products.
  - Switch to using the .xfdl file extension for your 
    applications. This is a long-term solution.
  
  If you have repeated problems with the .xfd file 
  extension, we recommend switching the .xfdl extension.

-------------
4.2  Printing
-------------

4.2.1  Form Not Printing Properly

  If a form does not print properly, try using the latest
  printer driver for your printer. We strongly recommend 
  using Postscript printer drivers, as they have been 
  more rigorously tested by their manufacturers.  
     
  To eliminate printing problems such as missing pages, 
  select "Put all form pages in one print job" in the 
  Printing section of Viewer Preferences (click the 
  Viewer's Preferences button in a form's toolbar, and 
  click Printing Options).

-----------------
4.3  Web Browsers
-----------------

4.3.1  Linking with Netscape 4.x as Default Browser

  If you are using Netscape 4.x as the default browser and
  you have multiple profiles in Netscape, you may experience 
  problems linking to another document.  When you perform a 
  link while the Viewer is open in standalone mode, Netscape 
  will be launched to open the document you are linking to.

  However, if you have more than one profile set up in 
  Netscape, you will have to choose a profile before 
  Netscape can perform the link. If you do not choose a 
  profile immediately, the link will fail. This problem can 
  be solved by ensuring that Netscape is open before you 
  perform a link.

4.3.2  Reloaded Forms

  Because web browsers retain a cache of previously loaded 
  documents, reloading a form may bring up the copy already 
  in the cache. If you have altered the form on the server 
  and want to reload it, clear the cache first.
  
  NOTE: Netscape has both a disk cache and a memory cache. 
  Clear both.
   
  If you are using Netscape, you also need to set the 
  browser to verify documents every time:
  
  1. Under Options, click Network Preferences and choose the
     Cache tab.
     
  2. For Verify Documents, select Every Time. 
  
  3. Click OK.
 
-------------------
4.4  Emailing Forms
-------------------

4.4.1  Emailing Large Forms Using the Viewer's Mail Form

  If you email a large form (approximately 1 meg or larger) 
  using the Viewer's mail form (rather than your own email 
  client), the large form may be truncated.  As a result, 
  the recipient will not be able to open the form.  This 
  problem can be solved by using a MAPI email client (that 
  is, your default email client) instead of the Viewer's 
  mail form.  This can be set in the Viewer's Preferences 
  form (be sure that your email client is also set up as 
  your default MAPI client). 

------------------
4.5  Signing Forms
------------------

4.5.1  Viewer Cannot Locate Interlink Signature Pad

  In some cases, the Viewer may not be able to to locate
  an Interlink signature pad, even if the signature pad is 
  present and all drivers are installed correctly.  This 
  occurs if the Windows process named wisptis.exe is 
  running, which may be started by certain Adobe products.
  This interference appears to be a general Interlink 
  problem that is not specific to the PureEdge Viewer.

  To determine whether this is the problem, open your Task
  Manager and look for wisptis.exe.  If the process is 
  running, you can end the task in the Task Manager.  Once 
  this process is stopped, the Viewer should be able to 
  locate the Interlink signature pad.  However, be aware 
  that this is a temporary fix, and that running other Adobe 
  programs may cause the problem to return.

  For a more permanent solution, you may need to remove the
  wisptis.exe file from your computer.  This requires 
  modifying several registry entries.  For more information
  about this process, we recommend searching the Internet
  for up to date information.                                                                                